Workaround issues with loading same module more than once
ClosedPublic

Authored by adamwill on Apr 13 2017, 10:30 PM.

Details

Summary

Loading the same module more than once *kinda* works, but it
shows up all kinds of funky in the openQA web interface. There's
a POO for this:
https://progress.opensuse.org/issues/10514
But it doesn't seem like it's going to be resolved immediately,
so in the mean time maybe we should avoid doing it so we don't
have to deal with the weirdness it produces in the web UI. So
here's a kinda icky hack that uses symlinks and stuff to load
multiple instances of 'the same' test module.

Test Plan

Run an update test, look at how it looks in the web
UI and confirm it's a lot clearer and less buggy. Check there
aren't any bugs in the loading approach. This is deployed on stg
so you can look at it there.

Diff Detail

Repository
rOPENQATESTS os-autoinst-distri-fedora
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
adamwill created this revision.Apr 13 2017, 10:30 PM
jsedlak accepted this revision.Apr 18 2017, 10:11 AM

Hmm, I don't particularly like this (adding new symlink each time we want to run some module more than once?), but it's necessary I guess and it works OK, so until upstream fixes this...

This revision is now accepted and ready to land.Apr 18 2017, 10:11 AM

"adding new symlink each time we want to run some module more than once?"

yep :/

"so until upstream fixes this..."

yeah, that's basically it. At first I looked at coming up with a patch, but it involves touching a *lot* of stuff. It'd be like a three, four day project just to patch it. I couldn't justify that over doing this, which took twenty minutes.

This revision was automatically updated to reflect the committed changes.