-
Notifications
You must be signed in to change notification settings - Fork 2
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
Rework TestScope
model to meet Servo's needs
#103
base: main
Are you sure you want to change the base?
Conversation
2b1b260
to
23e21e4
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
browser: Browser, | ||
visibility: TestVisibility, | ||
pub(crate) enum ServoTestScope { | ||
WebGpu, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From @sagudev on the commit (original link):
Maybe add some rustdoc comment that would describe variant. Something about that this is WebGPU CTS directory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is nitpicking but source
sounds wired to me in this context, maybe Servo tree
or Servo repo
would be more appropriate?
Disclaimer: I am NOT a native speaker.
…tead of `let-else`
23e21e4
to
daa3f73
Compare
In #92, I had suggested a new representation for
TestScope
whereBrowser
andTestVisibility
were two dimensions on which other products could integrate withmoz-webgpu-cts
. However, that model is wrong; Servo only really has one set of paths and runner URLs that it cares about, currently. One can observe this with thetodo!()
s that I merged in that PR. 😅 So, I'm fixing my mistake!Throw away
TestVisibility
and makeTestScope
mirrorBrowser
variants with additional, independent structure per-browser. Concretely, makeTestScope
use either aFirefoxTestScope
or aServoTestScope
, the latter of which only has aWebGpu
variant (for now).