The 'test runner' in this case is just the name of a regular module file, which happens to be used for running lots of tests, most of which look like EntryPoints. Nothing too magic going on here, and I've gotten this error by running modules for more 'normal' gwt apps as well, typically when I stop SDM, restart it, and then refresh the browser or click Compile without first using the SDM off bookmarklet.
> I'm not completely aware of your configuration but... it appears that > you're using incremental compiles from a test runner, and this test runner > isn't restricting the permutations to just 1. And that is being caught by > an assertion. > > You can fix this by adding some <set-property> tags to your test .gwt.xml > files. > > I hadn't thought of this use case, so I'm not sure if it's fair to tell > people to restrict their permutation or if we need to find a better way. > Thoughts? > Does this mean that we expect all projects to already be confined to one permutation, either via set-property or collapse-all-permutations? Is there no way to achieve that synthetically? Further, does this mean that one cannot test in multiple browsers simultaneously, for example re-compiling in FF until some behavior is satisfactory, then moving to Chrome (at least without stopping and restarting SDM)? -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/cdf99604-44c9-41b5-9cca-4f45227a3c89%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
