Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proxy-cmdline fails (spuriously?) due to lack of .treeinfo request #12

Closed
AdamWill opened this issue Apr 5, 2016 · 3 comments
Closed

Comments

@AdamWill
Copy link
Contributor

AdamWill commented Apr 5, 2016

so working on my openQA kickstart-tests runner, the proxy-cmdline test fails with .treeinfo request was not proxied. However, when I run the test interactively to check on it, it seems like the proxying all works perfectly well - I can tail -f /tmp/proxy.log and see all sorts of other stuff get proxied, including the two other things the check would look for - but there just isn't a .treeinfo request, it seems.

anyone have ideas on this? is it a genuine bug the test is catching? is it something different in my config when run in openQA? is the test borked?

I'm running the test on F24 Alpha Server netinst for now, to reproduce just run an install with inst.ks=https://www.happyassassin.net/ks/tests/proxy-cmdline.ks inst.proxy=http://127.0.0.1:8080 and poke around in /tmp/proxy.log while it's installing...you can see my parsed version of the kickstart at that URL. https://www.happyassassin.net/temp/proxy-cmdline.log is the proxy.log from a test run (after package download has completed, while install is running).

@AdamWill AdamWill changed the title proxy-cmdline fails spuriously due to lack of .treeinfo request proxy-cmdline fails (spuriously?) due to lack of .treeinfo request Apr 5, 2016
@AdamWill
Copy link
Contributor Author

AdamWill commented Apr 7, 2016

so we know what this is now: it's because I'm using a mirrorlist. we have a fix, just deciding how much more change to make to the proxy tests (if any) since I had some ideas.

@jkonecny12
Copy link
Member

Is this issue still valid or it could be closed now?

@AdamWill
Copy link
Contributor Author

I'm pretty sure 847bce8 would've fixed it.

jkonecny12 added a commit to jkonecny12/kickstart-tests that referenced this issue Nov 27, 2024
Introduced by changes in:
rhinstaller/anaconda#6018

Ignores this message:
```
10:26:59,558 DEBUG anaconda:anaconda: misc: GLib: rhinstaller#12(anaconda:2630): Gtk-rhinstaller#33[1;35mCRITICAL#033[0m **: rhinstaller#33[34m10:26:59.551#033[0m: gtk_widget_set_child_visible: assertion '!_gtk_widget_is_toplevel (widget)' failed
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants